Initial draft of MEX best practice #23
Conversation
|
This will require internal MathWorks review before it's merged into main. |
There was a problem hiding this comment.
Looks good.
I'm glad this is its own standalone document and not part of the main Toolbox Design doc.
At the top, maybe give etymology of MEX as "MATLAB EXecutable file".
"Let's explore the world of MEX integration!" This sounds a little too ChatGPT chirpy.
Maybe mention earlier that the actual compiled MEX files themselves are derived via the build process and so don't even appear in the folder. We only see, for example, subtract.m and subtract.cpp.
We should be clear about the fact that derived files shouldn't be checked into revision control. The whole concept of derived files is alien to a lot of our pure MATLAB users (i.e. they never really trained on any other language or language ecosystem).
Typo? line 47 "mex function" => "MEX function"?
The proposed organization is meant for toolboxes that implement MEX functions using C/ C++/ Fortran for implementing features. They might also interface with external libraries.